Skip to content

Update ECK upgrade doc to include a tip #742

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

Update ECK upgrade doc to include a tip #742

wants to merge 1 commit into from

Conversation

kunisen
Copy link
Contributor

@kunisen kunisen commented Mar 12, 2025

Based on an internal sync that I had with @pebrc recently, I'd like to add a tip to the ECK upgrade doc that,

  • ECK 2.x can upgrade to ECK 3.0.0 directly, without having to go to ECK 2.x latest minor version - 2.16

Please beg with me that I don't have experience posting doc PRs in this new repo and this is my first time 🙏

Things I am unsure and I'd appreciate if anyone could help me with:

Thanks!

@kunisen kunisen requested a review from pebrc March 12, 2025 07:08
@kunisen kunisen added the documentation Improvements or additions to documentation label Mar 12, 2025
@kunisen
Copy link
Contributor Author

kunisen commented Mar 12, 2025

Hi I just saw this sentence which perfectly describes the situation of skipping other versions and upgrading directly.

Note that the release notes and highlights only list the changes since the last release. If during the upgrade you skip any intermediate versions and go for example from 1.0.0 directly to 2.16.1, review the release notes and highlights of each of the skipped releases to understand all the breaking changes you might encounter during and after the upgrade.

So I think we don't need to call this small context out explicitly.
I will prepare an Elastic knowledge article for that later to describe some more details.

@kunisen kunisen closed this Mar 12, 2025
@eedugon
Copy link
Contributor

eedugon commented Mar 12, 2025

@kunisen , thanks a lot for collaborating with the new docs system, feel free to ping me in private if you need any help in the future. FYI here you have the guide for contributors, where the syntax and everything is shown: https://elastic.github.io/docs-builder/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@pebrc pebrc Awaiting requested review from pebrc

Assignees

No one assigned

Labels

documentation Improvements or additions to documentation

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@kunisen @eedugon